home *** CD-ROM | disk | FTP | other *** search
-
- Each field is a sperate entity including the
- H addresss......it is seached from right to left.....
-
- so if the address is:
-
- SB all @ xyz.#subregion.State.Country.Continent
-
- This will be scanned or parsed from the continental designator towards
- the left until it finds a match.....
-
- so if the address was
-
- SB all @ MN.USA.NA
-
- it would first look at at NA and disregard it because I am already in
- in the domain of NA. The same with USA. I'm not in MN, so that will
- be used for forwarding.
-
- Now the address can also be broken down so that SB all @ allus would work to
- without any H address...this is called a distributor and would fwd based on
- ALLUS to specific callsigns as set in the dist.mb file....these type of flooders
- do not go in the fwding file and are not attached to any Hroute as in FBB.
-
- So the main result is that my fwding file information contains the following
- information based on domains.
-
- 1> if the @ bbs field is a local system it forwards based on the @bbs
- field....ie sp n6xyz @ wa6rdh.#nocal.ca.usa.na would forward on wa6rdh
- as he is in my domain.
-
- 2> If the @ bbs field is not within my local domain but adjactent domains
- within the next biggest domain then the sub regional desigantor is used
- for fwding.....ie sp n6xyz @ w6ll.#cenca.ca.na.usa the #cenca is used
- for fwding..
-
- 3) the Domain of CA is completely ignored as I am in that domain and the
- local bbs plus the subregions are also within that domain.
-
- 4) If the @bbs field is not known and the subregional domain is not known
- and the state domain is known then it is used.
- e.g. sp k0zxf @ k0zxf.#tpa.fl.usa.na the fl is used for fwding.....
-
- 5) If the domain is outside of the 50 states, but still in NA,
- then the country domain is used.
-
- 6) If the domain is outside NA then the continental domain is used.
-
- 7) Flooders are used to distribute to to specific direct stations.
- The hierachical location information is ignored.
-
- mrybay - my lan
- allcan - northern calif
- allca - all of calif
- allusw - Western US
- allus - all of the US
- ww - the world
-
- These are directed to specific direct connect stations as designated
- in my dist.mb file which is a very small list.....they are then responsible
- for fwding this to the next station in the line, etc etc etc.
-
- 8> Now what this system fails to deal with is how we address messages to
- domains other than our own....hence the bulletins for addressing that
- I have sent out in the past to deal with the issue.....which is what
- you are alluding to in your request....yes we can use the H address
- to send traffic and address it to specific domains without problems.
-
- For example:
-
- SB all @ FL.USA.NA will work so will SB all @ fl.fl.usa.na
- SB all @ CAN.NA will work
- SB all @ EU.EU or SB all @ GBR.EU will work
-
- all will forward based on the domains that the system knows about.
-
- I did propose that we switch to such a system as did Brian, KA2BQE at
- one of the digital conferences.....based on the following:
-
- Local - @ bbs callsign
- Regional - Designator beginning with the '#' character.
- State - State, Province, Department, Prefecture, etc.
- ISO designator where available (e.g. CA, FL, OR)
- otherwise abbreviation in common use in the country.
- Country - 3 letter ISO designator.
- Continent - 2 letter ISO or 4 letter w3iwi designator.
-
- All that needs to be in your fwding system are the callsigns of other bbs
- in your Region, regional designators within your state (except for the
- Region you are in), state domains (except for the state you are in),
- country designators within your Continent (except for the Country you
- are in), and the Continetal names for continents other than your own.
-
- Very simple and does not require a raft of callsigns or designators.
-
-